Let runner implement the engine ABI for the engine worker. - #2118
Open
copybara-service[bot] wants to merge 1 commit into
Open
copybara-service[bot] wants to merge 1 commit into
copybara-service[bot] wants to merge 1 commit into
Conversation
copybara-service
Bot
force-pushed
the
cl/944563827
branch
14 times, most recently
from
July 10, 2026 13:29
c9460a2 to
93f5d00
Compare
copybara-service
Bot
force-pushed
the
cl/944563827
branch
from
July 22, 2026 20:28
93f5d00 to
0c43278
Compare
copybara-service
Bot
force-pushed
the
cl/944563827
branch
15 times, most recently
from
September 10, 2026 18:31
c0be67d to
479bc89
Compare
copybara-service
Bot
force-pushed
the
cl/944563827
branch
from
September 10, 2026 18:37
479bc89 to
b7ab396
Compare
copybara-service
Bot
force-pushed
the
cl/944563827
branch
from
September 18, 2026 19:35
b7ab396 to
75acb74
Compare
copybara-service
Bot
changed the title
copybara-service
Bot
force-pushed
the
cl/944563827
branch
5 times, most recently
from
September 24, 2026 15:06
ec99d2b to
039218b
Compare
This consolidates the duplicated controller interaction in runner and engine worker.
There is some unique interaction left in the runner:
- Dumping serailized FuzzTest config.
Needed so that one can pass the fuzzing options to the test binary command when directly using the controller. But this uses C++-based struct. We should either drop this or make it dump controller options as strings, as part of the engine ABI.
- Notifying the absense of custom mutator to use the controller's builtin mutator.
Technically the runner has its own mutator for LLVMFuzzerMutate, but it's using the legacy ByteArrayMutator for minimal dependency, while the controller has the FuzzTest-based mutator. This should not be a problem once we remove the legacy support in runner (and let legacy fuzzers use the FuzzTest LLVM fuzzer wrapper instead)
Also, move fork server to the engine worker because we need to make sure that fork server starts before handling persistent mode.
PiperOrigin-RevId: 944563827
copybara-service
Bot
force-pushed
the
cl/944563827
branch
from
September 25, 2026 15:05
039218b to
8bb4389
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Let runner implement the engine ABI for the engine worker.
This consolidates the duplicated controller interaction in runner and engine worker.
There is some unique interaction left in the runner:
Dumping serailized FuzzTest config.
Needed so that one can pass the fuzzing options to the test binary command when directly using the controller. But this uses C++-based struct. We should either drop this or make it dump controller options as strings, as part of the engine ABI.
Notifying the absense of custom mutator to use the controller's builtin mutator.
Technically the runner has its own mutator for LLVMFuzzerMutate, but it's using the legacy ByteArrayMutator for minimal dependency, while the controller has the FuzzTest-based mutator. This should not be a problem once we remove the legacy support in runner (and let legacy fuzzers use the FuzzTest LLVM fuzzer wrapper instead)
Also, move fork server to the engine worker because we need to make sure that fork server starts before handling persistent mode.